Device, method, and graphical user interface for mapping directions between search results

ABSTRACT

A method includes: displaying a map, a first field configured to receive a first query input, and a second field configured to receive a second query input; receiving the first query input in the first field; receiving the second query input in the second field; initiating a search that uses the first query input and a search that uses the second query input; concurrently displaying on the map a first plurality of search results for the first query input and a second plurality of search results for the second query input; detecting selection of a first search result in the first plurality of search results; detecting selection of a second search result in the second plurality of search results; and displaying a route on the map from the first search result to the second search result.

RELATED APPLICATIONS

This application is a continuation of PCT Patent Application No.PCT/US2010/020229, which was filed Jan. 6, 2010, which is incorporatedherein by reference in its entirety.

This application is related to the following applications: (1) U.S.patent application Ser. No. 11/969,211, “Portable Multifunction Device,Method, and Graphical User Interface for Providing Maps and Directions,”filed Jan. 3, 2008; (2) U.S. patent application Ser. No. 12/143,752,“Touch Screen Device, Method, and Graphical User Interface for ProvidingMaps, Directions, and Location-Based Information,” filed Jun. 20, 2008;and (3) U.S. patent application Ser. No. 12/566,668, “Device, Method,and Graphical User Interface for Providing Maps, Directions, andLocation-Based Information,” filed Sep. 25, 2009. All of theseapplications are incorporated by reference herein in their entirety.

TECHNICAL FIELD

This relates generally to electronic devices with displays, includingbut not limited to electronic devices with displays that map directions.

BACKGROUND

The use of electronic computing devices that provide directions hasincreased significantly in recent years. Exemplary electronic computingdevices that provide directions include navigation systems (e.g., globalpositioning system (GPS) navigation system). Such devices are widelyused to map directions.

Existing methods for integrating search results with mapping fordirections are cumbersome and inefficient. For example, it is quitetedious for a user to perform a first search for a starting point,identify a starting point in a first set of search results, perform asecond search for an ending point, identify an ending point in a secondset of second search results, and then enter the identified startingpoint and the identified ending point in a mapping application todetermine a route between the identified starting point and theidentified ending point. This process creates a significant cognitiveburden on the user. This process becomes even more tedious if the userwants to select a different search result for the starting point or theending point. It is well known that people have limited capacity ofshort-term memory and working memory. (See M. Daneman and P. Carpenter,“Individual differences in working memory and reading Journal of VerbalLearning & Verbal Behavior”, 19(4): 450-66 (1980); G. A. Miller, “Themagical number seven, plus or minus two: Some limits on our capacity forprocessing information”, Psychological Review, 63, 81-97 (1956)).Because of their limited memory capacity, users can easily forgetresults of previous searches, and thus have to repeat the same searches.Furthermore, users can have difficulty relating results of a previoussearch with results of a later search. These problems reduce efficiencyand productivity. In addition, existing methods take longer thannecessary, thereby wasting energy. This latter consideration isparticularly important in battery-operated devices.

SUMMARY

Accordingly, there is a need for computing devices with faster, moreefficient methods and interfaces for integrating search results withmapping for directions. Such methods and interfaces may complement orreplace conventional methods for mapping directions. Such methods andinterfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges.

The above deficiencies and other problems associated with userinterfaces for computing devices are reduced or eliminated by thedisclosed devices. In some embodiments, the device is a desktopcomputer. In some embodiments, the device is portable (e.g., a notebookcomputer, tablet computer, or handheld device). In some embodiments, thedevice has a touchpad. In some embodiments, the device has atouch-sensitive display (also known as a “touch screen” or “touch screendisplay”). In some embodiments, the device has a voice recognitionsystem. In some embodiments, the device has a graphical user interface(GUI), one or more processors, memory and one or more modules, programsor sets of instructions stored in the memory for performing multiplefunctions. In some embodiments, the user interacts with the GUIprimarily through finger contacts and gestures on the touch-sensitivesurface. In some embodiments, the functions may include image editing,drawing, presenting, word processing, website creating, disk authoring,spreadsheet making, game playing, telephoning, video conferencing,e-mailing, instant messaging, workout support, digital photographing,digital videoing, web browsing, digital music playing, and/or digitalvideo playing. Executable instructions for performing these functionsmay be included in a computer readable storage medium or other computerprogram product configured for execution by one or more processors.

In accordance with some embodiments, a method is performed at acomputing device with a display. The method includes: displaying a map,a first field configured to receive a first query input, and a secondfield configured to receive a second query input. The method alsoincludes receiving the first query input in the first field; receivingthe second query input in the second field; initiating a search thatuses the first query input and a search that uses the second queryinput; and concurrently displaying on the map a first plurality ofsearch results for the first query input and a second plurality ofsearch results for the second query input. The method further includesdetecting selection of a first search result in the first plurality ofsearch results; detecting selection of a second search result in thesecond plurality of search results; and in response to detectingselection of the first search result and detecting selection of thesecond search result, displaying a route on the map from the firstsearch result to the second search result.

In accordance with some embodiments, a method is performed at acomputing device with a display and a touch-sensitive surface. Themethod includes: displaying a portion of a route on a map; and detectinga plurality of gestures at a location on the touch-sensitive surfacethat corresponds to a next step icon. The method also includes, for eachrespective gesture in the plurality of gestures: when the respectivegesture satisfies a first predefined condition, displaying an animationthat moves from a current waypoint to a next waypoint on the route anddisplaying a portion of the route that includes the next waypoint; andwhen the respective gesture satisfies a second predefined condition thatis distinct from the first predefined condition, displaying the portionof the route that includes the next waypoint without displaying theanimation that moves from the current waypoint to the next waypoint onthe route.

In accordance with some embodiments, a method is performed at acomputing device with a display. The method includes: displaying a mapon the display; while displaying the map, displaying a popup view with alist of prior query inputs; and detecting selection of a prior queryinput in the list of prior query inputs. The method also includes, inresponse to detecting selection of the prior query input in the list ofprior query inputs: initiating a search using the selected prior queryinput; and displaying on the map one or more search results for theselected prior query input.

In accordance with some embodiments, a computing device includes adisplay, one or more processors, memory, and one or more programs; theone or more programs are stored in the memory and configured to beexecuted by the one or more processors and the one or more programsinclude instructions for performing the operations of any of the methodsdescribed above. In accordance with some embodiments, a graphical userinterface on a computing device with a display, a memory, and one ormore processors to execute one or more programs stored in the memoryincludes one or more of the elements displayed in any of the methodsdescribed above, which are updated in response to inputs, as describedin any of the methods above. In accordance with some embodiments, acomputer readable storage medium has stored therein instructions whichwhen executed by a computing device with a display, cause the device toperform the operations of any of the methods described above. Inaccordance with some embodiments, a computing device includes: adisplay; and means for performing the operations of any of the methodsdescribed above. In accordance with some embodiments, an informationprocessing apparatus, for use in a computing device with a display,includes means for performing the operations of any of the methodsdescribed above.

Thus, computing devices with displays are provided with faster, moreefficient methods and interfaces for integrating search results withmapping for directions, thereby increasing the effectiveness,efficiency, and user satisfaction with such devices. Such methods andinterfaces may complement or replace conventional methods for mappingdirections.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the aforementioned embodiments of theinvention as well as additional embodiments thereof, reference should bemade to the Description of Embodiments below, in conjunction with thefollowing drawings in which like reference numerals refer tocorresponding parts throughout the figures.

FIGS. 1A and 1B are block diagrams illustrating portable multifunctiondevices with touch-sensitive displays in accordance with someembodiments.

FIG. 1C is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIGS. 4A and 4B illustrate exemplary user interfaces for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4C illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIGS. 5A-5EEE illustrate exemplary user interfaces for mappingdirections between search results in accordance with some embodiments.

FIGS. 6A-6B are flow diagrams illustrating a method of mappingdirections between search results in accordance with some embodiments.

FIG. 7A-7B are flow diagrams illustrating a method of mapping portionsof a route in accordance with some embodiments.

FIGS. 8A-8C are flow diagrams illustrating a method of displaying apopup view with a list of prior query inputs in accordance with someembodiments.

DESCRIPTION OF EMBODIMENTS

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the present invention. However, it will beapparent to one of ordinary skill in the art that the present inventionmay be practiced without these specific details. In other instances,well-known methods, procedures, components, circuits, and networks havenot been described in detail so as not to unnecessarily obscure aspectsof the embodiments.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first contact could be termed asecond contact, and, similarly, a second contact could be termed a firstcontact, without departing from the scope of the present invention. Thefirst contact and the second contact are both contacts, but they are notthe same contact.

The terminology used in the description of the invention herein is forthe purpose of describing particular embodiments only and is notintended to be limiting of the invention. As used in the description ofthe invention and the appended claims, the singular forms “a”, “an” and“the” are intended to include the plural forms as well, unless thecontext clearly indicates otherwise. It will also be understood that theterm “and/or” as used herein refers to and encompasses any and allpossible combinations of one or more of the associated listed items. Itwill be further understood that the terms “includes,” “including,”“comprises,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof.

As used herein, the term “if” may be construed to mean “when” or “upon”or “in response to determining” or “in response to detecting,” dependingon the context. Similarly, the phrase “if it is determined” or “if [astated condition or event] is detected” may be construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

As used herein, the term “query input” refers to query inputs (e.g.,search terms) concerning search results, where at least a subset of thesearch results are to be displayed on a map.

As used herein, the terms “speech recognition” are “voice recognition”are used interchangeably to refer to audio inputs based on speech and/orvoice. As used herein, the term “voice command” refers to audio inputsbased on speech and/or voice that initiate respective actions indevices.

Embodiments of computing devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the computing device is a portable communications devicesuch as a mobile telephone that also contains other functions, such asPDA and/or music player functions. Exemplary embodiments of portablemultifunction devices include, without limitation, the iPhone® and iPodTouch® devices from Apple Inc. of Cupertino, Calif. Other portabledevices such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads) may also beused. It should also be understood that, in some embodiments, the deviceis not a portable communications device, but is a desktop computer witha touch-sensitive surface (e.g., a touch screen display and/or a touchpad).

In the discussion that follows, a computing device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the computing device may include one or moreother physical user-interface devices, such as a physical keyboard, amouse and/or a joystick. Furthermore, the computing device may include avoice recognition system.

The device supports a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that may be executed on the device may use atleast one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the device maybe adjusted and/or varied from one application to the next and/or withina respective application. In this way, a common physical architecture(such as the touch-sensitive surface) of the device may support thevariety of applications with user interfaces that are intuitive andtransparent to the user.

The user interfaces may include one or more soft keyboard embodiments.The soft keyboard embodiments may include standard (QWERTY) and/ornon-standard configurations of symbols on the displayed icons of thekeyboard, such as those described in U.S. patent application Ser. No.11/459,606, “Keyboards For Portable Electronic Devices,” filed Jul. 24,2006, and Ser. No. 11/459,615, “Touch Screen Keyboards For PortableElectronic Devices,” filed Jul. 24, 2006, the contents of which arehereby incorporated by reference in their entireties. The keyboardembodiments may include a reduced number of icons (or soft keys)relative to the number of keys in existing physical keyboards, such asthat for a typewriter. This may make it easier for users to select oneor more icons in the keyboard, and thus, one or more correspondingsymbols. The keyboard embodiments may be adaptive. For example,displayed icons may be modified in accordance with user actions, such asselecting one or more icons and/or one or more corresponding symbols.One or more applications on the device may utilize common and/ordifferent keyboard embodiments. Thus, the keyboard embodiment used maybe tailored to at least some of the applications. In some embodiments,one or more keyboard embodiments may be tailored to a respective user.For example, one or more keyboard embodiments may be tailored to arespective user based on a word usage history (lexicography, slang,individual usage) of the respective user. Some of the keyboardembodiments may be adjusted to reduce a probability of a user error whenselecting one or more icons, and thus one or more symbols, when usingthe soft keyboard embodiments.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIGS. 1A and 1B are block diagramsillustrating portable multifunction devices 100 with touch-sensitivedisplays 112 in accordance with some embodiments. Touch-sensitivedisplay 112 is sometimes called a “touch screen” for convenience, andmay also be known as or called a touch-sensitive display system. Device100 may include memory 102 (which may include one or more computerreadable storage mediums), memory controller 122, one or more processingunits (CPU's) 120, peripherals interface 118, RF circuitry 108, audiocircuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem106, other input or control devices 116, and external port 124. Device100 may include one or more optical sensors 164. These components maycommunicate over one or more communication buses or signal lines 103.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 may have more orfewer components than shown, may combine two or more components, or mayhave a different configuration or arrangement of the components. Thevarious components shown in FIGS. 1A and 1B may be implemented inhardware, software, or a combination of both hardware and software,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 may include high-speed random access memory and may alsoinclude non-volatile memory, such as one or more magnetic disk storagedevices, flash memory devices, or other non-volatile solid-state memorydevices. Access to memory 102 by other components of device 100, such asCPU 120 and the peripherals interface 118, may be controlled by memorycontroller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU 120, and memorycontroller 122 may be implemented on a single chip, such as chip 104. Insome other embodiments, they may be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 may include well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 may communicate with networks, such as the Internet, alsoreferred to as the World Wide Web (WWW), an intranet and/or a wirelessnetwork, such as a cellular telephone network, a wireless local areanetwork (LAN) and/or a metropolitan area network (MAN), and otherdevices by wireless communication. The wireless communication may useany of a plurality of communications standards, protocols andtechnologies, including but not limited to Global System for MobileCommunications (GSM), Enhanced Data GSM Environment (EDGE), high-speeddownlink packet access (HSDPA), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over InternetProtocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet messageaccess protocol (IMAP) and/or post office protocol (POP)), instantmessaging (e.g., extensible messaging and presence protocol (XMPP),Session Initiation Protocol for Instant Messaging and PresenceLeveraging Extensions (SIMPLE), Instant Messaging and Presence Service(IMPS)), and/or Short Message Service (SMS), or any other suitablecommunication protocol, including communication protocols not yetdeveloped as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 may include display controller 156 andone or more input controllers 160 for other input or control devices.The one or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input controldevices 116 may include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 may becoupled to any (or none) of the following: a keyboard, infrared port,USB port, and a pointer device such as a mouse. The one or more buttons(e.g., 208, FIG. 2) may include an up/down button for volume control ofspeaker 111 and/or microphone 113. The one or more buttons may include apush button (e.g., 206, FIG. 2). A quick press of the push button maydisengage a lock of touch screen 112 or begin a process that usesgestures on the touch screen to unlock the device, as described in U.S.patent application Ser. No. 11/322,549, “Unlocking a Device byPerforming Gestures on an Unlock Image,” filed Dec. 23, 2005, which ishereby incorporated by reference in its entirety. A longer press of thepush button (e.g., 206) may turn power to device 100 on or off. The usermay be able to customize a functionality of one or more of the buttons.Touch screen 112 is used to implement virtual or soft buttons and one ormore soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 andconverts the detected contact into interaction with user-interfaceobjects (e.g., one or more soft keys, icons, web pages or images) thatare displayed on touch screen 112. In an exemplary embodiment, a pointof contact between touch screen 112 and the user corresponds to a fingerof the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touch pads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from portable device 100,whereas touch sensitive touch pads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a resolution in excess of 100 dpi. In someembodiments, the touch screen has a resolution of approximately 160 dpi.The user may make contact with touch screen 112 using any suitableobject or appendage, such as a stylus, a finger, and so forth. In someembodiments, the user interface is designed to work primarily withfinger-based contacts and gestures, which can be less precise thanstylus-based input due to the larger area of contact of a finger on thetouch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

In some embodiments, device 100 may include a physical or virtual wheel(e.g., a click wheel) as input control device 116. A user may navigateamong and interact with one or more graphical objects (e.g., icons)displayed in touch screen 112 by rotating the click wheel or by moving apoint of contact with the click wheel (e.g., where the amount ofmovement of the point of contact is measured by its angular displacementwith respect to a center point of the click wheel). The click wheel mayalso be used to select one or more of the displayed icons. For example,the user may press down on at least a portion of the click wheel or anassociated button. User commands and navigation commands provided by theuser via the click wheel may be processed by input controller 160 aswell as one or more of the modules and/or sets of instructions in memory102. For a virtual click wheel, the click wheel and click wheelcontroller may be part of touch screen 112 and display controller 156,respectively. For a virtual click wheel, the click wheel may be eitheran opaque or semitransparent object that appears and disappears on thetouch screen display in response to user interaction with the device. Insome embodiments, a virtual click wheel is displayed on the touch screenof a portable multifunction device and operated by user contact with thetouch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIGS. 1Aand 1B show an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 may include charge-coupleddevice (CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device, so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for videoconferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 may also include one or more proximity sensors 166. FIGS. 1Aand 1B show proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 may also include one or more accelerometers 168. FIGS. 1A and1B show accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are which are incorporated byreference herein in their entirety. In some embodiments, information isdisplayed on the touch screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreaccelerometers. Device 100 optionally includes, in addition toaccelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASSor other global navigation system) receiver (not shown) for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments memory 102 stores device/global stateinformation 157, as shown in FIGS. 1A and 1B. Device/global stateinformation 157 includes one or more of: active application state,indicating which applications, if any, are currently active; displaystate, indicating what applications, views or other information occupyvarious regions of touch screen display 112; sensor state, includinginformation obtained from the device's various sensors and input controldevices 116; and location information concerning the device's locationand/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, oran embedded operating system such as VxWorks) includes various softwarecomponents and/or drivers for controlling and managing general systemtasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact/motion module 130 may detect contact with touch screen 112 (inconjunction with display controller 156) and other touch sensitivedevices (e.g., a touchpad or physical click wheel). Contact/motionmodule 130 includes various software components for performing variousoperations related to detection of contact, such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, may include determining speed (magnitude), velocity(magnitude and direction), and/or an acceleration (a change in magnitudeand/or direction) of the point of contact. These operations may beapplied to single contacts (e.g., one finger contacts) or to multiplesimultaneous contacts (e.g., “multitouch”/multiple finger contacts). Insome embodiments, contact/motion module 130 and display controller 156detects contact on a touchpad. In some embodiments, contact/motionmodule 130 and controller 160 detects contact on a click wheel.

Contact/motion module 130 may detect a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns. Thus, a gesture may be detected by detecting a particularcontact pattern. For example, detecting a finger tap gesture includesdetecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) asthe finger-down event (e.g., at the position of an icon). As anotherexample, detecting a finger swipe gesture on the touch-sensitive surfaceincludes detecting a finger-down event followed by detecting one or morefinger-dragging events, and subsequently followed by detecting afinger-up (lift off) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the intensity of graphics that aredisplayed. As used herein, the term “graphics” includes any object thatcan be displayed to a user, including without limitation text, webpages, icons (such as user-interface objects including soft keys),digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic may be assigned a corresponding code.Graphics module 132 receives, from applications etc., one or more codesspecifying graphics to be displayed along with, if necessary, coordinatedata and other graphic property data, and then generates screen imagedata to output to display controller 156.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   video player module 145;    -   music player module 146;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which merges video player        module 145 and music player module 146;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, contactsmodule 137 may be used to manage an address book or contact list (e.g.,stored in application internal state 192 of contacts module 137 inmemory 102 or memory 370), including: adding name(s) to the addressbook; deleting name(s) from the address book; associating telephonenumber(s), e-mail address(es), physical address(es) or other informationwith a name; associating an image with a name; categorizing and sortingnames; providing telephone numbers or e-mail addresses to initiateand/or facilitate communications by telephone 138, video conference 139,e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, telephone module138 may be used to enter a sequence of characters corresponding to atelephone number, access one or more telephone numbers in address book137, modify a telephone number that has been entered, dial a respectivetelephone number, conduct a conversation and disconnect or hang up whenthe conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,videoconferencing module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, e-mail client module 140 includes executable instructions tocreate, send, receive, and manage e-mail in response to userinstructions. In conjunction with image management module 144, e-mailclient module 140 makes it very easy to create and send e-mails withstill or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, map module 154, and music player module 146,workout support module 142 includes executable instructions to createworkouts (e.g., with time, distance, and/or calorie burning goals);communicate with workout sensors (sports devices); receive workoutsensor data; calibrate sensors used to monitor a workout; select andplay music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, image management module 144 includes executable instructionsto arrange, modify (e.g., edit), or otherwise manipulate, label, delete,present (e.g., in a digital slide show or album), and store still and/orvideo images.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, audio circuitry 110, and speaker 111,video player module 145 includes executable instructions to display,present or otherwise play back videos (e.g., on touch screen 112 or onan external, connected display via external port 124).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, music player module 146includes executable instructions that allow the user to download andplay back recorded music and other sound files stored in one or morefile formats, such as MP3 or AAC files. In some embodiments, device 100may include the functionality of an MP3 player, such as an iPod(trademark of Apple Inc.).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail client module 140, and browser module 147, calendarmodule 148 includes executable instructions to create, display, modify,and store calendars and data associated with calendars (e.g., calendarentries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 may beused by a user to create widgets (e.g., turning a user-specified portionof a web page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134,search module 151 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 102 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, notes module153 includes executable instructions to create and manage notes, to dolists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 maybe used to receive, display, modify, and store maps and data associatedwith maps (e.g., driving directions; data on stores and other points ofinterest at or near a particular location; and other location-baseddata) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, online video module 155 includes instructionsthat allow the user to access, browse, receive (e.g., by streamingand/or download), play back (e.g., on the touch screen or on anexternal, connected display via external port 124), send an e-mail witha link to a particular online video, and otherwise manage online videosin one or more file formats, such as H.264. In some embodiments, instantmessaging module 141, rather than e-mail client module 140, is used tosend a link to a particular online video. Additional description of theonline video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the content of which is herebyincorporated by reference in its entirety.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various embodiments. For example, video player module 145may be combined with music player module 146 into a single module (e.g.,video and music player module 152, FIG. 1B). In some embodiments, memory102 may store a subset of the modules and data structures identifiedabove. Furthermore, memory 102 may store additional modules and datastructures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that may be performed exclusivelythrough a touch screen and/or a touchpad include navigation between userinterfaces. In some embodiments, the touchpad, when touched by the user,navigates device 100 to a main, home, or root menu from any userinterface that may be displayed on device 100. In such embodiments, thetouchpad may be referred to as a “menu button.” In some otherembodiments, the menu button may be a physical push button or otherphysical input control device instead of a touchpad.

FIG. 1C is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIGS. 1A and 1B) or 370 (FIG. 3) includes event sorter170 (e.g., in operating system 126) and a respective application 136-1(e.g., any of the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is(are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177 or GUI updater 178 to update the application internalstate 192. Alternatively, one or more of the application views 191includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and lift-off of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact with one another. In some embodiments, metadata183 includes configurable properties, flags, and/or lists that indicatewhether sub-events are delivered to varying levels in the view orprogrammatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater176 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens, e.g.,coordinating mouse movement and mouse button presses with or withoutsingle or multiple keyboard presses or holds, user movements taps,drags, scrolls, etc., on touch-pads, pen stylus inputs, movement of thedevice, oral instructions, detected eye movements, biometric inputs,and/or any combination thereof, which may be utilized as inputscorresponding to sub-events which define an event to be recognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screen maydisplay one or more graphics within user interface (UI) 200. In thisembodiment, as well as others described below, a user may select one ormore of the graphics by making contact or touching the graphics, forexample, with one or more fingers 202 (not drawn to scale in the figure)or one or more styluses 203 (not drawn to scale in the figure). In someembodiments, selection of one or more graphics occurs when the userbreaks contact with the one or more graphics. In some embodiments, thecontact may include a gesture, such as one or more taps, one or moreswipes (from left to right, right to left, upward and/or downward)and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someembodiments, inadvertent contact with a graphic may not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon may not select the corresponding application when the gesturecorresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, Subscriber Identity Module(STM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 may be used to turn the power on/off on thedevice by depressing the button and holding the button in the depressedstate for a predefined time interval; to lock the device by depressingthe button and releasing the button before the predefined time intervalhas elapsed; and/or to unlock the device or initiate an unlock process.In an alternative embodiment, device 100 also may accept verbal inputfor activation or deactivation of some functions through microphone 113.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320may include circuitry (sometimes called a chipset) that interconnectsand controls communications between system components. Device 300includes input/output (I/O) interface 330 comprising display 340, whichis typically a touch screen display. I/O interface 330 also may includea keyboard and/or mouse (or other pointing device) 350 and touchpad 355.Memory 370 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM or other random access solid state memory devices; and mayinclude non-volatile memory, such as one or more magnetic disk storagedevices, optical disk storage devices, flash memory devices, or othernon-volatile solid state storage devices. Memory 370 may optionallyinclude one or more storage devices remotely located from CPU(s) 310. Insome embodiments, memory 370 stores programs, modules, and datastructures analogous to the programs, modules, and data structuresstored in memory 102 of portable multifunction device 100 (FIG. 1), or asubset thereof. Furthermore, memory 370 may store additional programs,modules, and data structures not present in memory 102 of portablemultifunction device 100. For example, memory 370 of device 300 maystore drawing module 380, presentation module 382, word processingmodule 384, website creation module 386, disk authoring module 388,and/or spreadsheet module 390, while memory 102 of portablemultifunction device 100 (FIG. 1) may not store these modules.

Each of the above identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of the aboveidentified modules corresponds to a set of instructions for performing afunction described above. The above identified modules or programs(i.e., sets of instructions) need not be implemented as separatesoftware programs, procedures or modules, and thus various subsets ofthese modules may be combined or otherwise re-arranged in variousembodiments. In some embodiments, memory 370 may store a subset of themodules and data structures identified above. Furthermore, memory 370may store additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that may be implemented on portable multifunction device 100.

FIGS. 4A and 4B illustrate exemplary user interfaces for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400A includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Phone 138, which may include an indicator 414 of the number            of missed calls or voicemail messages;        -   E-mail client 140, which may include an indicator 410 of the            number of unread e-mails;        -   Browser 147; and        -   Music player 146; and    -   Icons for other applications, such as:        -   IM 141;        -   Image management 144;        -   Camera 143;        -   Video player 145;        -   Weather 149-1;        -   Stocks 149-2;        -   Workout support 142;        -   Calendar 148;        -   Calculator 149-3;        -   Alarm clock 149-4;        -   Dictionary 149-5; and        -   User-created widget 149-6.

In some embodiments, user interface 400B includes the followingelements, or a subset or superset thereof:

-   -   402, 404, 405, 406, 141, 148, 144, 143, 149-3, 149-2, 149-1,        149-4, 410, 414, 138, 140, and 147, as described above;    -   Map icon for map module 154;    -   Notes icon for notes module 153;    -   Settings 412, which provides access to settings for device 100        and its various applications 136, as described further below;    -   iPod icon for video and music player module 152, also referred        to as iPod (trademark of Apple Inc.) module 152; and    -   Online video icon for online video module 155, also referred to        as YouTube (trademark of Google Inc.) module 155.

FIG. 4C illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Although many of the examples which followwill be given with reference to inputs on touch screen display 112(where the touch sensitive surface and the display are combined), insome embodiments, the device detects inputs on a touch-sensitive surfacethat is separate from the display, as shown in FIG. 4C. In someembodiments the touch sensitive surface (e.g., 451 in FIG. 4C) has aprimary axis (e.g., 452 in FIG. 4C) that corresponds to a primary axis(e.g., 453 in FIG. 4C) on the display (e.g., 450). In accordance withthese embodiments, the device detects contacts (e.g., 460 and 462 inFIG. 4C) with the touch-sensitive surface 451 at locations thatcorrespond to respective locations on the display (e.g., in FIG. 4C 460corresponds to 468 and 462 corresponds to 470). In this way, user inputs(e.g., contacts 460 and 462, and movements thereof) detected by thedevice on the touch-sensitive surface (e.g., 451 in FIG. 4C) are used bythe device to manipulate the user interface on the display (e.g., 450 inFIG. 4C) of the multifunction device when the touch-sensitive surface isseparate from the display. It should be understood that similar methodsmay be used for other user interfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input, stylus input,keyboard input, or voice input). For example, a tap gesture may bereplaced with a mouse click while the cursor is located over thelocation of the tap gesture (e.g., instead of detection of the contactfollowed by ceasing to detect the contact). As another example, a voiceinput may be used to activate objects on a display (e.g., a voicecommand “next” may activate a “next” or “next step” icon on thedisplay). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice may beused simultaneously, or a mouse and finger contacts may be usedsimultaneously.

In the descriptions provided below, the term “contact” (except when usedto describe an entry in a contact list, address book or the like) isused as a short hand term for “touch gesture,” and thus each contactmentioned or described below may be any suitable touch gesture detectedby a sensor (or set of sensors) of a touch-sensitive display or othertouch-sensitive surface. Similarly, each “finger tap” mentioned ordescribed below may be any suitable touch gesture. Furthermore, in someembodiments, “touch gestures” include not only gestures, made by one ormore fingers or one or more styluses, that make physical contact atouch-sensitive screen 112 or other touch-sensitive surface, but alsogestures that occur, in whole or in part, sufficiently close totouch-sensitive screen 112 or other touch-sensitive surface that the oneor more sensors of touch-sensitive screen 112 or other touch-sensitivesurface are able to detect those gestures.

In the context of the embodiments described below, user-initiated“searches” are performed in the context of a map program (e.g., mapmodule 154) that works in conjunction with an online map application.For example, in some embodiments, when a user-initiated search isperformed for a search query of “hotel,” the search query “hotel” istransmitted by map module 154 of device 100 (or 300) to an online serverproviding mapping application services, and in response device 100 (or300) receives map information. Map module 154 renders the received mapinformation on display 112 (or 340) of device 100 (or 300). In thisexample, the map information received by the device includes a road mapor other map for a particular geographic area (e.g., the geographic areasurrounding the user's current location, or a geographic areacorresponding to a geographic location last specified by the user) and aset of objects (e.g., search result pins) indicating map locations ofhotels. There are numerous types of map searches, as described below,and the information returned to device 100 (or 300) in response to thesearch depends on the information requested. In other embodiments, a mapdatabase is locally stored in device 100 (or 300) in memory 102 (or 370)and user-initiated searches are performed locally by searching thelocally stored map database.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on a multifunctiondevice with a display and a touch-sensitive surface, such as device 300or portable multifunction device 100.

FIGS. 5A-5EEE illustrate exemplary user interfaces for mappingdirections between search results in accordance with some embodiments.The user interfaces in these figures are used to illustrate theprocesses described below, including the processes in FIGS. 6A-6B,7A-7B, and 8A-8C.

FIG. 5A depicts an exemplary user interface displaying map 520 in amapping application on touch screen 112. The mapping application mayinclude the following elements, or a subset or superset thereof:

-   -   search mode icon 508 that when activated (e.g., by a finger tap        on the icon) initiates the display of a map in a search mode; in        the search mode, the map is configured to overlay search        results; in this example, the search mode icon is activated, and        as a result, the search mode icon is highlighted with a bold        outline;    -   directions mode icon 510 that when activated (e.g., by a finger        tap on the icon) initiates the display of a map in a directions        mode; in the directions mode, the map is configured to overlay        directions;    -   view location icon 512 that when activated (e.g., by a finger        tap on the icon) initiates various modes, such as a tracked mode        or a heading mode;    -   bookmark icon 514 that when activated (e.g., by a finger tap on        the icon) initiates the display of bookmarks and/or contacts;        and    -   search term input area 516 that when activated (e.g., by a        finger tap on the icon) initiates receiving search terms for a        location search (e.g., search terms can be a full or partial        address, or a name of a business or a person).

The exemplary user interface depicted in FIG. 5A also includes signalintensity indicator 502 (which indicates the intensity of the radiocommunication signal, such as signal for Wi-Fi, EDGE, and 3G), currenttime indicator 504, and battery power indicator 506.

In FIG. 5A, current location indicator 598-1 of the device is displayedon the map 520. In some embodiments, current location indicator 598-1represents an approximate location of the device. FIG. 5A alsoillustrates a detection of contact 505 at a location on the touch screen112 corresponding to (e.g., at or near) search field 516 (which is anexample of a text entry field).

In FIG. 5B, in response to detecting contact 505, recents popup view540-1 and keyboard 542 are displayed. Recents popup view 540-1 includesa list of recent query inputs. A user can provide query inputs byselecting one of the query inputs listed in recents popup view 540, orby typing one or more keywords on keyboard 542.

FIG. 5B also illustrates that contact 507-A is detected at a location ontouch screen 112 corresponding to recents popup view 540-1. In FIG. 5C,contact 507 has moved to a different location (e.g., 507-B), and aportion of recents popup view 540-1 has scrolled in accordance with themovement of contact 507.

FIG. 5D illustrates that a user has initiated typing a keyword onkeyboard 542. In this example, contact 509 is detected at a location onkeyboard 542 corresponding to the key “H”. In FIG. 5D, in response todetecting contact 509, recents popup view 540-1 changes to suggestionspopup view 540-2, and the character “H” is displayed in search terminput area 516. Suggestions popup view 540-2 displays suggested keywordsthat at least partially match the input received via the keyboard. Inthis example, suggestions popup view 540-2 displays suggested keywordsthat start with the provided search term character, “h,” and optionallydisplays one or more suggested keyword phrases (e.g., “Thomas Holmes”,the last name of which starts with an “h”) having at least one word thatstarts with the provided search term character, “h.” In addition, deleteicon 578 is displayed within the search term input area 516. Delete icon578 when activated (e.g., by a finger tap on the icon) deletes theentire entry, if any, in search term input area 516.

In FIG. 5E, contact 511 is detected at a location on keyboard 542corresponding to the key “O”. In response to detecting contact 511, thecharacter “o” is additionally displayed in search term input area 516,and suggestions popup view 540-3 displays suggested keywords that startwith (or that include a word that starts with) the user-providedcharacters, “ho”.

FIG. 5F illustrates that the search term input area 516 contains asearch term, “Hotel”. The search term “Hotel” can be provided by usingkeys on keyboard 542 as described above. In FIG. 5F, a gesture (e.g.,contact 513-A) is detected at a location corresponding to a searchinitiation icon (e.g., search key 544). In response, a search isinitiated to search for locations that correspond to the search term,“hotel”. Alternatively, a contact 513-A′ at one of the suggestedkeywords 546 that corresponds to the search keyword, “hotel” (in thisexample, the suggested keyword 546-1) initiates the same search,regardless of the entry already in search input area 516 (e.g., even ifsearch input area 516 were to contain a different search term, such as“coffee”, a contact on the suggested keyword, “hotel” initiates a searchfor locations that correspond to the search term, “hotel”).

FIGS. 5G-5H illustrate an animation displaying search results on map520. In FIG. 5G, search result pins (522-1 and 522-2) appear from anedge of touch screen 112 and move toward the locations corresponding tothe search results. Also, pin shadows (548-1 and 548-2) or other visualeffects may appear and move toward the locations corresponding to thesearch results. In addition, special indicator 582-1 appears and movestoward the location corresponding to a search result of specialdesignation (e.g., a location selected by a sponsor, a popular location,etc.). In other embodiments, the search result pins may be animated in adifferent manner, or may appear on the map without an animation.

In FIG. 5H, callout 524-1 is displayed adjacent to search result pin522-1. Callout 524-1 includes information text (e.g., name of theperson, business, or building, type of a building/facility, address,etc.) associated with the corresponding location. In this example,callout 524-1 includes the name of business or building, “ABC Hotel,”associated with the corresponding location. Callout 524-1 may alsoinclude street view icon 528 that when activated (e.g., by a finger tapon the icon, or by a voice command) initiates the display of a streetview at the corresponding location; and/or information icon 526 thatwhen activated (e.g., by a finger tap on the icon, or by a voicecommand) initiates the display of additional information associated withthe corresponding location (e.g., a phone number and/or a websiteaddress of a person or business at the corresponding location).

In FIG. 5I, contact 515 is detected at a location on touch screen 112corresponding to directions mode icon 510. Contact 515 (or anyequivalent user command) causes the map application to display a userinterface in the directions mode.

FIG. 5J illustrates an exemplary user interface in the directions mode.The exemplary user interface may include the following elements, asubset or superset thereof:

-   -   starting point input area 570 that displays a starting point for        a route; starting point input area 570 when activated (e.g.,        selected by a finger tap on the icon, or by a voice command)        enables input of a search query for the starting point, as        described with respect to FIGS. 5A-F;    -   ending point input area 572 that displays an ending point for        the route; ending point input area 572 when activated (e.g.,        selected by a finger tap on the icon, or by a voice command)        enables input of a search query for the ending point, as        described with respect to FIGS. 5A-F;    -   starting points list icon 574-1 that when activated (e.g., by a        finger tap on the icon, or by a voice command) initiates the        display of a list of starting points (e.g., query results for        starting points, or a list of recently selected locations);    -   ending points list icon 574-2 than when activated (e.g., by a        finger tap on the icon, or by a voice command) initiates the        display of a list of ending points (e.g., query results for        ending points, or a list of recently selected locations);    -   reverse-route icon 576 that when activated initiates one or more        of the following: switching the starting points and ending        points (i.e., converting starting points to ending points, and        converting ending points to starting points), switching an entry        in starting point input area 570 and an entry in ending point        input area 572, and updating directions;    -   route 580-1, which indicates a route from a selected starting        point to a selected ending point; in some embodiments, device        100 selects a starting point and an ending point based on        predefined criteria; in this example, the device's current        location (represented by current location indicator 598-1) is        selected as a starting point, and search result pin 522-1 is        selected as an ending point;    -   directions popup view 530 that displays information associated        with a route from a starting point to an ending point; in some        embodiments, the information displayed in directions popup view        530 includes travel directions; in this example, the directions        popup view 530 indicates the distance and travel time for route        580-1 to the ending point, ABC Hotel for a respective mode of        travel (“driving”);    -   mode of travel icons 532 that when activated (e.g., by a finger        tap on the icon, or by a voice command) initiate the selection        of a mode of travel, and optionally update route 580-1 and/or        directions popup view 530 (e.g., display an updated route and        associated information for the selected mode of travel); in this        example, mode of travel icons 532 include driving icon 532-1,        public transportation icon 532-2, and walking icon 532-3; and    -   start directions icon 534 that when activated (e.g., by a finger        tap on the icon, or by a voice command) initiate the display of        directions for the route from the selected starting point to the        selected ending point.

Also in FIG. 5J, search result pins 522 become ending point searchresult pins. In other words, previous search results becomeuser-selectable ending points. Depending on whether the reverse routeicon is activated, these search results could also become userselectable starting points.

In FIG. 5K, contact 517 is detected at a location on touch screen 112corresponding to (e.g., at or near) ending points list icon 574-2. Inresponse, results popup view 540-4 is displayed in FIG. 5L. Resultspopup view 540-4 includes a list of query results obtained from aprevious search for locations that correspond to the search query,“hotel.”

FIG. 5L also illustrates that contact 519 is detected at a location ontouch screen 112 outside results popup view 540-4. In response, resultspopup view 540-4 ceases to display (or disappears), as shown in FIG. 5M.

FIG. 5M also illustrates that contact 521 is detected at a location ontouch screen 112 that corresponds to search result pin 522-2, therebyselecting search result pin 522-2. In response to contact 521, route580-1 ceases to display (or disappears), and route 580-2 from currentlocation 598-1 to search result pin 522-2 is displayed, as shown in FIG.5N. In addition, callout 524-1 ceases to display (or disappears), andcallout 524-2 is displayed. Optionally, callout 524-2 includes streetview icon 528 and information icon 526 as described above. Directionspopup view 530 displays information associated with route 580-2.Optionally, directions popup view 530 also includes icons 532-1, 532-2,532-3, and 534 as described above.

In FIG. 5O, contact 523 is detected at a location on touch screen 112that corresponds to starting point input area 570. In response, recentspopup view 540-5 and keyboard 542 are displayed, as shown in FIG. 5P.Recents popup view 540-5 (FIG. 5P) includes a list of recent searchqueries (also called query inputs) 546 for starting points. In FIG. 5Q,contact 525 is detected at a location on touch screen 112 thatcorresponds to recent query input 546-7. In response, a search isinitiated to search for locations that correspond to the search query,“coffee”. FIGS. 5R-5S illustrate changes to the user interface of themap application resulting for initiation of the search for locationsthat correspond to the search query, “coffee”.

In particular, FIGS. 5R-5S illustrate an animation of displaying searchresults (for the search query, “coffee”) on map 520. In FIG. 5R,starting point search result pins (536-1 and 536-2) and pin shadows(548-3 and 548-4) appear as described above. In addition, route 580-2ceases to display (or disappears); and route 580-3 from starting pointsearch result pin 536-2 to ending point search result pin 522-2 andcallout 524-3 are displayed. In this example, ending point search resultpins (536-1 and 536-2) and starting point search result pins (522-1 and522-2) are visually distinguished by having different colors, patternsor shading. In some embodiments, pin shadows for starting point searchresult pins (e.g., 548-1 and 548-2) and pin shadows for ending pointsearch result pins (e.g., 548-3 and 548-3) are visually distinguished byhaving different colors, patterns or shading.

In FIG. 5S, contact 527 is detected at a location on touch screen 112that corresponds to ending point input area 572. In response, the mapapplication displays recents popup view 540-6 and keyboard 542, as shownin FIG. 5T. Recents popup view 540-6 includes a list of recent searchqueries for ending points. In this example, recent pop up view 540-6 forending points and recent popup view 540-5 for starting points (in FIG.5P) have distinct lists of recent query inputs (i.e., the list of recentquery inputs for starting points and the list of recent query inputs forending points are not identical). For example, recents popup view 540-6(for ending points) includes search terms: restaurant, computer, and aname of a person, John Doe. None of these are included in recents popupview 540-5. However, in some other embodiments, the same recents popupview is provided for both starting points and ending points. Optionally,recents popup view 540-6 includes recently selected map locations and/orrecent location search queries of all types (for map locations, forstarting points and for ending points).

FIG. 5T also illustrates that contact 529 is detected at a location ontouch screen 112 that corresponds to an area outside recents popup view540-6. In response, the map application ceases to display recents popupview 540-6, as shown in FIG. 5U.

FIG. 5U illustrates detection of contact 531 at a location on touchscreen 112 that corresponds to reverse-route icon 576. In response, thestarting points and the ending points are switched, as shown in FIG. 5V.For example, search input areas 570 and 572 display hotel as a queryinput for starting points and coffee as a query input for ending points.Starting point search result pins 522-1 and 522-2 are converted toending point search result pins 536-3 and 536-4. Similarly, ending pointsearch result pins 536-1 and 536-2 are converted to starting pointsearch result pins 522-3 and 522-4. Directions popup view 530 displaysinformation associated with the route from starting point search resultpin 536-4 to ending point search result pin 522-4.

FIG. 5W illustrates detection of contact 533 at a location on touchscreen 112 that corresponds to reverse-route icon 576. In response, thestarting points and the ending points are switched back, as shown inFIG. 5X.

FIG. 5X also illustrates detection of contact 535 at a location on touchscreen 112 that corresponds to starting point search result pin 536-1,thereby selecting starting point search result pin 536-1. In response,the map application ceases to display route 580-3, and instead displaysroute 580-4 from starting point search result pin 536-1 to ending pointsearch result pin 522-2, as shown in FIG. 5Y. In addition, callout 524-4(for starting point search result pin 536-1) is displayed.

FIG. 5Z illustrates detection of contact 537 at a location on touchscreen 112 that corresponds to ending point search result pin 522-1,thereby selecting ending point search result pin 522-1. In response, themap application ceases to display route 580-4, and instead displaysroute 580-5 from starting point search result pin 536-1 to ending pointsearch result pin 522-1, as shown in FIG. 5AA

In FIG. 5BB, contact 539 is detected at a location on touch screen 112for a period longer than a predefined duration. In some embodiments, thepredefined duration is a fixed length of time between 0.2 and 2 seconds(e.g., 1 second). In response, the map application adds a user-moveablemarker, herein called a “dropped pin,” to the map 520, as shown in FIGS.5CC-5DD.

FIGS. 5CC-5DD illustrate an animation of displaying the user-movablelocation marker (dropped pin 538-1) being added to map 520. Dropped pin538-1, pin shadow 548-5, and callout 524-5 appear as described above. Inaddition, the map application ceases to display route 580-5, and insteaddisplays route 580-6 from starting point search result pin 536-1 todropped pin 538-1, as shown in FIG. 5DD. Dropped pin 538-1 is visuallydistinguished from starting point search result pins 522 and endingpoint search result pins 536 by having different colors, patterns orshading. In some embodiments, pin shadow 548-5 for dropped pin 538-1 isvisually distinguished from pin shadows for starting point search resultpins and ending point search result pins. In FIG. 5DD, the “End” field572 has not been updated with the location of the dropped pin, but insome embodiments a reverse lookup may be used to determine the addressof the location of the dropped pin, and the address may be automaticallyentered in either the start or end field, as appropriate.

FIGS. 5EE-5HH illustrate an animation of moving dropped pin 538-1 inaccordance with user-controlled movement of contact 541. In FIG. 5EE,contact 541-A is detected at a location on touch screen 112corresponding to dropped pin 538-1. As contact 541 moves, dropped pin538-1 appears unplugged (FIG. 5FF), follows contact 541 (FIG. 5GG), anddrops (FIG. 5HH) to a location corresponding to the location of a lastcontact (541-C in FIG. 5GG). In some embodiments, the appearance of thedropped pin may not change while it is being manipulated or moved on themap. In addition, route 580-7 from a starting point search result pin536-1 to a new location of dropped pin 538-1 is displayed.

In FIG. 5II, contact 543 is detected at a location on touch screen 112corresponding to reverse-route icon 576. In response, the startingpoints and the ending points are switched, as described above and shownin FIG. 5JJ. Directions popup view 530 displays information about aroute from dropped pin 538-1 to ending point search result pin 522-3.

FIGS. 5KK and 5LL illustrate a snapping process in the mappingapplication. In FIG. 5KK, contact 545 is detected, for a period longerthan the predefined duration, at a location on touch screen 112corresponding to a physical location to which an ordinary vehicle or anordinary person cannot travel (e.g., a body of water such as an ocean,lake, or river, or a forested or mountainous area without roads). Forexample, contact 545-A is detected at a location corresponding to themiddle of an airport (e.g., a runway). Similarly, contact 545-A′ isdetected at a location corresponding to a location in the middle of ariver channel. Airport runways and river channels are not areas to whichan ordinary vehicle or an ordinary person travels. FIG. 5LL illustratesthat dropped pins 538-2 and 538-3 are deposited at locationscorresponding to physical locations to which an ordinary vehicle or anordinary person can travel (e.g., via public roads), adjacent tocontacts 545-A and 545-A′. In some embodiments, when contact 545 isdetected at an inaccessible location, the dropped pin is placed at anintersection, street, airport terminal, park, beach, or other publiclyaccessible point closest to contact 545.

FIG. 5MM-5EEE illustrate exemplary user interfaces for displayingportions of a route in accordance with some embodiments.

FIG. 5MM depicts an exemplary map application user interface displayingmap 520 on touch screen 112. The user interface may include thefollowing elements, or a subset or superset thereof:

-   -   starting point search result pins 536-5 and 536-6, as described        above;    -   ending point search result pins 522-5 and 522-6, as described        above;    -   directions popup view 530, as described above; and    -   start directions icon 534, as described above.

FIG. 5MM illustrates route 580-8 from starting point search result pin536-6 to ending point search result pin 522-6. FIG. 5MM also illustratesthat contact 547 is detected at a location on touch screen 112 thatcorresponds to start directions icon 534. In response to contact 547,the map application displays portions of route 580-8 are displayed onmap 520, as shown in FIG. 5NN. In addition, the map application displayswaypoints 554-1, 554-2, and 554-3 on map 520. FIG. 5NN illustrates thatdirections popup view 530 displays a portion of the route from a currentwaypoint (e.g., 554-1) to a next waypoint (e.g., 554-2). Waypoints arepoints on the route. In some embodiments, waypoints are points on theroute where the direction of travel changes or where the routetransitions from one roadway or sub-route to another roadway orsub-route. Optionally, as shown in FIG. 5NN, directions popup view 530includes:

-   -   previous step icon 550-1 that when activated (e.g., by a finger        tap on the icon, or by a voice command) initiates the display of        a previous portion of the route; and    -   next step icon 550-2 that when activated (e.g., by a finger tap        on the icon, or by a voice command) initiates the display of a        next portion of the route.

FIG. 5NN also illustrates detection of contact 549 at a location ontouch screen 112 that corresponds to next step icon 550-2. In someembodiments, the map application responds to contact 549 at a locationon touch screen 112 that corresponds to next step icon 550-2 bydisplaying an animation that moves from a current waypoint (e.g., 554-1)to the next waypoint (e.g., 554-2), as shown in FIGS. 500-5RR. In FIGS.500-5RR, location indicator 552 is used to indicate advancement from thecurrent waypoint to the next waypoint.

In FIG. 5RR, the next portion of the route (e.g., a portion of routefrom waypoint 554-2 to waypoint 554-3) is displayed. In someembodiments, displaying the next portion of the route includes visuallydistinguishing the next portion of the route from a remainder of theuntraveled route. In this example, the next portion of the route isvisually distinguished by having difference color, pattern, and/or linewidth. FIG. 5RR also illustrates that directions popup view 530 displaysdirections for the next portion of the route.

In FIG. 5SS, contact 551 is detected at a location on touch screen 112that corresponds to next step icon 550-2. In some embodiments, inresponse to contact 551 at a location on touch screen 112 thatcorresponds to next step icon 550-2, the map application displays ananimation of location indicator 552 that moves from waypoint 554-2 towaypoint 554-3, as shown in FIG. 5TT.

In FIG. 5TT, while the animation is displayed, contacts 553-A and 553-Bare detected at a location on touch screen 112 that corresponds to nextstep icon 550-2. In some embodiments, in response to contacts 553-A and553-B at a location on touch screen 112 that corresponds to next stepicon 550-2, the animation of location indicator 552 that moves fromwaypoint 554-2 to waypoint 554-3 is ceased (or terminated), and locationindicator 552 is displayed at waypoint 554-3, as shown in FIG. 5UU.

In FIG. 5VV, a portion of the route from waypoint 554-3 to waypoint554-4 is displayed (and/or visually distinguished from other portions ofroute 580-8). Location indicator 552 is displayed at a locationcorresponding to waypoint 554-3. The map application transitions fromthe view in FIG. 5VV to the view in FIG. 5WW in accordance withpredefined criteria, as discussed below with reference to operation 706,shown in FIG. 7A.

In FIG. 5WW, a portion of the route from waypoint 554-4 to waypoint554-5 is displayed. Location indicator 552 is displayed at a locationcorresponding to waypoint 554-4 (i.e., at the next waypoint along theroute after the waypoint identified by location indicator 552 in FIG.5VV). FIG. 5WW also illustrates detection of contacts 555-A, 555-B, and555-C at a location on touch screen 112 that corresponds to next stepicon 550-2.

FIGS. 5XX-5YY illustrate an exemplary user interface with an animationin an entire route view. In FIGS. 5XX-5YY, the entire route of route580-8 is displayed. Location indictor 552 is displayed on a portion ofthe route from waypoint 554-4 to waypoint 554-5. In some embodiments,location indicator 552 is displayed with an animation visuallyindicating advancement from waypoint 554-4 to waypoint 554-5. FIG. 5XXalso illustrates detection of contacts 557-A, 557-B, and 557-C at alocation on touch screen 112 that corresponds to next step icon 550-2.Similarly, FIG. 5YY also illustrates detection of contacts 559-A, 559-B,and 559-C at a location on touch screen 112 that corresponds to nextstep icon 550-2.

FIG. 5ZZ-5AAA depict a similar animation in the entire route view. InFIG. 5ZZ, contacts 561-A, 561-B, and 561-C are detected at a location ontouch screen 112 that corresponds to next step icon 550-2. In FIG. 5AAA,contacts 563-A and 563-B are detected at a location on touch screen 112that corresponds to next step icon 550-2. The map application determineshow to update the user interface in accordance with a rate of (or timedifference between) contacts 563-A and 563-B, as explained below withreference to FIG. 7A.

In FIG. 5BBB, a portion of the route from waypoint 554-6 to waypoint554-7 is displayed (and/or visually distinguished from other options ofroute 580-8). FIGS. 5BBB-5CCC also illustrate an animation of locationindicator 552 moving from waypoint 554-6 to waypoint 554-7. In FIG.5CCC, contact 565 is detected at a location on touch screen 112 thatcorresponds to next step icon 550-2.

Similarly, in FIGS. 5DDD-5EEE, a portion of the route from waypoint554-7 to waypoint 554-8 is displayed (and/or visually distinguished fromother options of route 580-8). FIGS. 5DDD-5EEE also illustrate ananimation of location indicator 552 moving from waypoint 554-7 towaypoint 554-8. FIG. 5EEE illustrates a completion of the animation.

FIGS. 6A-6B are flow diagrams illustrating method 600 of mappingdirections between search results in accordance with some embodiments.Method 600 is performed at a computing device (e.g., device 300, FIG. 3,or portable multifunction device 100, FIG. 1) having a display. In someembodiments, the device has a touch-sensitive surface. In someembodiments, the display is a touch screen display and thetouch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. Some operations inmethod 600 may be combined and/or the order of some operations may bechanged.

As described below, method 600 provides an intuitive way to mapdirections between search results. The method reduces the cognitiveburden on a user when mapping directions between search results, therebycreating a more efficient human-machine interface. For example, when auser searches for both starting points and ending points, conventionalmethods require that the user perform searches respectively for thestarting points and the ending points. Such multiple searches aretedious. In comparison, simultaneous display of search results for bothstarting points and ending points enables faster and more optimalselection of a starting point and an ending point (e.g., simultaneousdisplay of hotels and coffee shops allows selection of a hotel that ismost closely located to a coffee shop). For battery-operated computingdevices, enabling a user to map directions between search results fasterand more efficiently conserves power and increases the time betweenbattery charges.

Device 100 displays (602) a map, a first field configured to receive afirst query input, and a second field configured to receive a secondquery input (e.g., in a browser 147 or a dedicated mapping application154). For example, in FIG. 5J, touch screen 112 displays map 520, afirst field configured to receive a first query input (e.g., startingquery input area 570), and a second field configured to receive a secondquery input (e.g., ending point input area 572). The first field isdistinct from the second field (e.g., starting point input area 570 isdistinct from ending point input area 572). The map, first field, andsecond field are typically displayed concurrently (e.g., FIG. 5J).

Device 100 receives (604) the first query input in the first field(e.g., via a physical keyboard, finger or stylus gestures on a softkeyboard, or speech recognition of audio input). For example, the firstquery input in starting point input area 570 is provided by contact 525on a prior query input listed in recents popup view 540-5 (FIG. 5Q).Device 100 receives (606) the second query input in the second field, ina similar manner (e.g., recents popup view 540-6 in FIG. 5T can be usedto provide the second query input in the second field).

In some embodiments, the second query input in the second fieldcorresponds to a query input received in a third field. For example, aquery input in the ending point input area 572 corresponds to a queryinput received in search term input area 516 (FIGS. 5I-5J).

Device 100 initiates (608) a search that uses the first query input anda search that uses the second query input. The search(es) may beperformed at the computing device and/or at a remote server that cancommunicate with the computing device (e.g., a search engine server).

Device 100 concurrently displays (610) on the map a first plurality ofsearch results for the first query input and a second plurality ofsearch results for the second query input (e.g., starting point searchresult pins 522-1 and 522-2 and ending point search result pins 536-1and 536-2 on map 520 in FIG. 5S).

Device 100 detects (612) selection (by a user) of a first search resultin the first plurality of search results (e.g., via detecting a fingeror stylus gesture on the first search result, detecting a mouse clickwhen a cursor is positioned over the first search result, or speechrecognition of audio input; for example, contact 535 on starting pointsearch result pin 536-1 in FIG. 5X). In some embodiments, selection of afirst search result in the first plurality of search results includesselection of the first search result in accordance with a firstpredefined criteria without a user's individual selection. For example,starting point search result pin 536-2 is selected without a user'sindividual selection (e.g., a contact) in FIG. 5S. The predefinedcriteria includes one or more of the following elements: proximity to acurrent location, proximity to a major road, proximity to the center ofthe map; and the sequence or ranking of the search results.

Device 100 detects (614) selection (by the user) of a second searchresult in the second plurality of search results (e.g., via detecting afinger or stylus gesture on the second search result, detecting a mouseclick when a cursor is positioned over the second search result, orspeech recognition of audio input); for example, contact 537 on endingpoint search result pin 522-1 in FIG. 5Z). In some embodiments,selection of a second search result in the second plurality of searchresults includes selection of the second search result in accordancewith a second predefined criteria without a user's individual selection.For example, ending point search result pin 522-1 is selected without auser's individual selection (e.g., a contact) in FIG. 5J. The secondpredefined criteria is as described above. In some embodiments, thefirst predefined criteria is distinct from the second predefinedcriteria. In other embodiments, the first predefined criteria and thesecond criteria are identical.

In response to detecting selection of the first search result anddetecting selection of the second search result, device 100 displays(616) a route on the map from the first search result to the secondsearch result (e.g., route 580-5 in FIG. 5AA). The route may includedirections for a car, a bus, or a walker (e.g., directions popup view530 in FIG. 5AA may include directions).

In various embodiments, additional steps and/or limitations can beimplemented (e.g., sec 618 in FIG. 6B).

In some embodiments, the first plurality of search results are routestarting points and the second plurality of search results are routeending points (620). For example, the first plurality of search resultsfor the first query input (e.g., query input in starting point inputarea 570) are route starting points (e.g., starting point search resultpins 522) in FIG. 5S. Similarly, the second plurality of search resultsfor the second query input (e.g., query input in ending point input area572) are route ending points (e.g., ending point search result pins 536)in FIG. 5S.

In some embodiments, while displaying the route on the map between thefirst search result and the second search result, device 100 detects(622) selection of a reverse-route icon (e.g., via detecting a finger orstylus gesture on the reverse-route icon, detecting a mouse click when acursor is positioned over the reverse-route icon, or speech recognitionof audio input; for example, contact 531 on reverse-route icon 576 inFIG. 5U). In response to detecting selection of a reverse-route icon:device 100 converts the first plurality of search results to routeending points and the second plurality of search results to routestarting points (e.g., starting point search result pins 536-1 and 536-2are converted to ending point search result pins 522-3 and 522-4, andending point search result pins 522-1 and 522-2 are converted tostarting point search result pins 536-3 and 536-4 in FIGS. 5U-5V), andconverts the route to a route from the second query result to the firstquery result (e.g., directions popup view 530 indicates the reversal ofthe route in FIGS. 5U-5V).

In some embodiments, while displaying the route on the map between thefirst search result and the second search result, device 100 detects(624) selection (by a user) of a third search result in the firstplurality of search results (e.g., via detecting a finger or stylusgesture on the third search result, detecting a mouse click when acursor is positioned over the third search result, or speech recognitionof audio input). In response to detecting selection of the third searchresult, the device ceases to display the route on the map from the firstsearch result to the second search result, and displays a route on themap from the third search result to the second search result (e.g., inresponse to detecting contact 535 on starting point search result pin536-1 in FIG. 5X, route 580-4 from starting point search result pin536-1 to ending point search result pin 522-2 is displayed in FIG. 5Y).

In some embodiments, while displaying the route on the map between thefirst search result and the second search result, device 100 detects(626) selection (by a user) of a third search result in the secondplurality of search results (e.g., via detecting a finger or stylusgesture on the third search result, detecting a mouse click when acursor is positioned over the third search result, or speech recognitionof audio input). In response to detecting selection of the third searchresult, device 100 ceases to display the route on the map from the firstsearch result to the second search result, and displays a route on themap from the first search result to the third search result (e.g., inresponse to detecting contact 537 on ending point search result pin522-1 in FIG. 5Z, route 580-5 from starting point search result pin536-1 to ending point search result pin 522-1 is displayed in FIG. 5AA).

In some embodiments, while displaying the route on the map between thefirst search result and the third search result, device 100 detects(628) selection (by a user) of a fourth search result in the firstplurality of search results (e.g., via detecting a finger or stylusgesture on the fourth search result, detecting a mouse click when acursor is positioned over the fourth search result, or speechrecognition of audio input). In response to detecting selection of thefourth search result, device 100 ceases to display the route on the mapfrom the first search result to the third search result, and displays aroute on the map from the fourth search result to the third searchresult (e.g., in response to detecting contact 537 on ending pointsearch result pin 522-1 in FIG. 5Z, route 580-5 from starting pointsearch result pin 536-1 to ending point search result pin 522-1 isdisplayed in FIG. 5AA).

In some embodiments, the first plurality of search results is visuallydistinguished (630) from the second plurality of search results (e.g.,by having different colors, patterns or shading, such as green pins forthe first plurality when the first plurality are candidate routestarting points and red pins for the second plurality when the secondplurality are candidate route ending points). For example, startingpoint search result pins 536 are visually distinguished from endingpoint search result pins 522 in FIGS. 5S-5AA.

FIGS. 7A-7B are flow diagrams illustrating method 700 of mappingportions of a route in accordance with some embodiments. Method 700 isperformed at a computing device (e.g., device 300, FIG. 3, or portablemultifunction device 100, FIG. 1) with a display and a touch-sensitivesurface. In some embodiments, the display is a touch screen display andthe touch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. Some operations inmethod 700 may be combined and/or the order of some operations may bechanged.

As described below, method 700 provides an intuitive way to displayportions of a route. The method reduces the cognitive burden on a userwhen displaying portions of a route, thereby creating a more efficienthuman-machine interface. For example, the method allows a user to see arelationship between a portion of a route and the entire route, therebyallowing a better comprehension of the route. In addition, the methodenables accelerated display of portions of a route, thereby reducing thepresentation time. For battery-operated computing devices, enabling auser to display portions of a route faster and more efficientlyconserves power and increases the time between battery charges.

Device 100 displays (702) a portion of a route on a map (e.g., in abrowser 147 or a dedicated mapping application 154). For example, aportion of a route (e.g., route 580-8) is displayed on map 520 in FIG.5NN. The route is from a starting waypoint to an ending waypoint (e.g.,route 580-8 in FIG. 5MM from starting point search result pin 536-6 toending point search result pin 522-6).

Device 100 detects (704) a plurality of gestures (e.g., tap gesturesmade with a finger or a stylus; contacts 549, 551, 553, 555, 557, 559,561, 563, and 565 in FIGS. 5NN-5CCC) at a location on thetouch-sensitive surface that corresponds to a next step (or nextwaypoint) icon (e.g., next step icon 550-2).

For each respective gesture in the plurality of gestures, when therespective gesture satisfies a first predefined condition (e.g., therespective gesture is detected after displaying the animation; the timebetween detecting the respective gesture and a previous gesture on thenext step icon is greater than a predefined duration; or the rate ofgestures detected on the next step icon increases less than a predefinedthreshold), device 100 displays (706) an animation that moves from acurrent waypoint to a next waypoint on the route and displays a portionof the route that includes the next waypoint (e.g., FIGS. 5NN-5QQ), andwhen the respective gesture satisfies a second predefined condition thatis distinct from the first predefined condition (e.g., the respectivegesture is detected while displaying the animation; the time betweendetecting the respective gesture and a previous gesture on the next stepicon is less than a predefined duration; or the rate of gesturesdetected on the next step icon increases more than a predefinedthreshold), device 100 displays the portion of the route that includesthe next waypoint without displaying the animation that moves from thecurrent waypoint to the next waypoint on the route (e.g., FIGS.5VV-5WW). In some embodiments, when the respective gesture satisfies thesecond predefined condition that is distinct from the first predefinedcondition, device 100 displays a shorter animation that moves from thecurrent waypoint to the next waypoint on the route and display theportion of the route that includes the next waypoint.

In some embodiments, the first predefined condition is satisfied (708)if the time between detecting the respective gesture and a previousgesture on the next step icon is greater than a predefined duration. Insome embodiments, the predefined duration is between 0.1 and 2 seconds(e.g., 0.5 seconds).

In some embodiments, when the respective gesture occurs after a previousgesture at the location on the touch-sensitive surface that correspondsto the next step icon, the first predefined condition is satisfied (710)if the respective gesture is detected after an animation correspondingto the previous gesture is completely displayed (e.g., contact 551 inFIG. 5SS). Stated in another way that is logically equivalent, the firstpredefined condition is satisfied (710) when the respective gestureoccurs after a previous gesture at the location on the touch-sensitivesurface that corresponds to the next step icon and the respectivegesture is detected after an animation corresponding to the previousgesture is completely displayed.

In some embodiments, the second predefined condition is satisfied (712)if the time between detecting the respective gesture and a previousgesture on the next step icon is less than a predefined duration. Insome embodiments, the predefined duration is between 0.1 and 2 seconds(e.g., 0.5 seconds).

In some embodiments, when the respective gesture occurs after a previousgesture at the location on the touch-sensitive surface that correspondsto the next step icon, the second predefined condition is satisfied(714) if the respective gesture is detected while an animationcorresponding to the previous gesture is displayed (contact 553-A orcontact 553-B in FIG. 5TT). Stated in another way that is logicallyequivalent, the second predefined condition is satisfied (714) when therespective gesture occurs after a previous gesture at the location onthe touch-sensitive surface that corresponds to the next step icon andthe respective gesture is detected while an animation corresponding tothe previous gesture is displayed.

In various embodiments, additional steps and/or limitations can beimplemented (e.g., see 716 in FIG. 7B).

In some embodiments, for each respective gesture in the plurality ofgestures, when the respective gesture satisfies a third predefinedcondition that is distinct from the first predefined condition and thesecond predefined condition (e.g., the time between detecting therespective gesture and a previous gesture on the next step icon is lessthan a predefined duration; the rate of gesture is more than apredefined rate), device 100 displays (718) the entire route andvisually indicates advancement to the next waypoint on the route. Forexample, in response to contacts 555-A, 555-B, and 555-C in FIG. 5WW,the entire route is displayed and visual indication of advancement tothe next waypoint is displayed in FIGS. 5WW-5YY.

In some embodiments, the third predefined condition is satisfied (720)if the time between detecting the respective gesture and a previousgesture on the next step icon is less than a predefined duration. Insome embodiments, the predefined duration is between 0.1 and 2 seconds(e.g., 0.3 seconds).

In some embodiments, the first, second, and third predefined conditionsinclude (722) the number of gestures at the location on thetouch-sensitive surface that corresponds to the next step icon during apredefined time interval. In some embodiments, the predefined timeinterval is between 0.2 and 2 seconds (e.g., 1 second). In someembodiments, the number of gestures that satisfy the third predefinedcondition is one to five gestures within one second (e.g., threegestures in one second), or a corresponding number of gestures at thesame rate of gestures for the predefined time interval (e.g., 2 gesturesin 0.67 seconds has substantially the same rate as three gestures in onesecond).

In some embodiments, after detecting one or more gestures that satisfythe third predefined condition, device 100 detects (724) satisfaction ofa fourth predefined condition (e.g., ceasing to detect another gestureon the next step icon for a predefined time period; the rate of thegestures on the next step icon is less than a predefined rate, whereinthe predefined rate is between one and four taps per second; or the rateof the gestures on the next step icon decreases by more than apredefined percentage). In response to detecting satisfaction of thefourth predefined condition, device 100 displays a portion of the routethat includes the next waypoint. In other words, the display transitionsfrom showing the entire route and the location of the next waypoint inthis overall route view to displaying just a portion of the route thatincludes the next waypoint. In some embodiments, this transition isanimated. For example, in FIGS. 5ZZ-5BBB, the number of gestures duringa respective predefined time interval decreases from three gestures inFIG. 5ZZ to two gestures in FIG. 5AAA. In response, device 100 ceases todisplay the entire route and displays a portion of the route in FIG.5BBB. In addition, in FIG. 5BBB, an animation of location indicator 552moving from waypoint 554-6 to waypoint 554-7 is displayed.

FIGS. 8A-8C are flow diagrams illustrating method 800 of displaying apopup view with a list of prior query inputs in accordance with someembodiments. Method 800 is performed at a computing device (e.g., device300, FIG. 3, or portable multifunction device 100, FIG. 1) with adisplay. In some embodiments, the device has a touch-sensitive surface.In some embodiments, the display is a touch screen display and thetouch-sensitive surface is on the display. In some embodiments, thedisplay is separate from the touch-sensitive surface. Some operations inmethod 800 may be combined and/or the order of some operations may bechanged.

As described below, method 800 provides an intuitive way to display apopup view with a list of prior query inputs. The method reduces thecognitive burden on a user when displaying a popup view with a list ofprior query inputs, thereby creating a more efficient human-machineinterface. For example, allowing a user to select a query input from thelist of prior query inputs improves accuracy (e.g., by avoidingtypographical errors associated with typing, and/or reducing errorsassociated with speech recognition of new query inputs) and efficiency(e.g., by avoiding having to provide a query input again). Concurrentdisplay of the list of prior query inputs and a portion of a map remindsthe user of the area of the map for which a search is to be initiated,thereby reducing the cognitive burden on the user. For battery-operatedcomputing devices, enabling a user to display a popup view with a listof prior query inputs faster and more efficiently conserves power andincreases the time between battery charges.

Device 100 includes a computing device with a display (802). Device 100displays (804) a map on the display (e.g., in a browser 147 or adedicated mapping application 154). For example, device 100 displays map520 on touch screen 112 in FIG. 5A.

While displaying the map, device 100 displays (806) a popup view with alist of prior query inputs (e.g., recents popup views 540-1 in FIG. 5B,540-5 in FIG. 5P, and 540-6 in FIG. 5T).

Device 100 detects (808) selection of a prior query input in the list ofprior query inputs (e.g., via detecting a gesture on the prior queryinput, detecting a mouse click when a cursor is positioned over theprior query input, or speech recognition of audio input). For example,contact 525 is detected on prior query input 546-7 in FIG. 5Q.

In response to detecting selection of the prior query input in the listof prior query inputs, device 100 initiates (810) a search using theselected prior query input, and displays on the map one or more searchresults for the selected prior query input (e.g., starting point searchresult pins 536 in FIGS. 5R-5S).

In some embodiments, initiating a search using the selected prior queryinput includes retrieving search results from a previous search usingthe selected prior query input. In some embodiments, retrieving searchresults from a previous search using the selected prior query inputincludes retrieving a subset of search results stored in device 100. Inother embodiments, retrieving search results from a previous searchusing the selected prior query input includes retrieving a subset ofsearch results stored in a remote server (e.g., a server providing mapinformation retrieval services).

In various embodiments, additional steps and/or limitations (e.g., see812 in FIG. 8B and 814 in FIG. 8C) may be implemented.

In some embodiments, the list of prior query inputs is scrollable (816)(e.g., recents popup view 540-1 is scrollable, as illustrated in FIGS.5B-5C).

In some embodiments, in response to detecting selection of the priorquery input in the list of prior query inputs, device 100 ceases todisplay the popup view (818) (e.g., in FIGS. 5Q-5R, after detectingcontact 525 on prior query input 546-7, the map application ceases todisplay recents popup view 540-5 on touch screen 112).

In some embodiments, the computing device includes (820) atouch-sensitive surface (e.g., a track pad or a touch-sensitivedisplay). Device 100 displays a keyboard on the display, detects agesture at a location on the touch-sensitive surface that corresponds tothe keyboard (e.g., a tap gesture on a key in the keyboard). In responseto detecting the gesture at the location on the touch-sensitive surfacethat corresponds to the keyboard, device 100 displays a suggestion boxthat includes a list of suggested query inputs (e.g., suggestions popupview 540-2 in FIG. 5D).

In some embodiments, displaying the suggestion box includes replacingthe list of prior query inputs with the list of suggested query inputs(822) (e.g., suggestions pop up view 540-2 replaces recents popup view540-1 in FIGS. 5C-5D).

In some embodiments, the list of suggested query inputs is generated(824) in accordance with input (e.g., input in a search field) receivedvia the keyboard (e.g., the respective list of suggested query inputs inFIGS. 5D-5E is generated in accordance with a query input in search terminput area 516).

In some embodiments, generating the list of suggested query inputsincludes (826) identifying an entry in an address book stored in thecomputing device (e.g., “Henry Doe” and “Thomas Holmes” in suggestionspopup view 540-2 may be entries in an address book stored in device100). The entry at least partially matches the input received via thekeyboard (e.g., “Henry Doe” starts with the character “h” received insearch term input area 516; similarly, the last name of “Thomas Holmes”starts with the character “h”).

In some embodiments, generating the list of suggested query inputsincludes (828) obtaining suggested query inputs from a remote server. Insome embodiments, the remote server is a search engine or a serverproviding map information retrieval services. In some embodiments, theremote server includes a map database.

In some embodiments, the computing device includes (830) atouch-sensitive surface (e.g., a track pad or a touch-sensitivedisplay), and device 100 detects selection of the prior query input bydetecting a gesture (e.g., a tap gesture made with a finger or a stylus)at a location on the touch-sensitive surface that corresponds to theprior query input (e.g., contact 525 at a location that corresponds toprior query input 546-7 in FIG. 5Q).

In some embodiments, the computing device includes (832) atouch-sensitive surface (e.g., a track pad or a touch-sensitivedisplay), and the popup view with the list of prior query inputs isdisplayed in response to detecting a gesture (e.g., a tap gesture madewith a finger or a stylus) at a location on the touch-sensitive surfacethat corresponds to a recent queries icon. For example, in someembodiments, list icon 574 in FIG. 5K when activated initiates thedisplay of the list of prior query inputs, such as recents popup view540-4 in FIG. 5L.

In some embodiments, the computing device includes (834) atouch-sensitive surface (e.g., a track pad or a touch-sensitivedisplay), and the popup view with the list of prior query inputs isdisplayed in response to detecting a gesture (e.g., a tap gesture madewith a finger or a stylus) at a location on the touch-sensitive surfacethat corresponds to one of: a first field configured to receive a firstquery input and a second field configured to receive a second queryinput. For example, in response to contact 523 in FIG. 5O, recents popupview 540-5 is displayed in FIG. 5P. In some embodiments, the first field(e.g., starting point input area 570) is a start field configured toreceive a starting location or a query (e.g., a query concerning thestart location of a route), and the second field (e.g., ending pointinput area 572) is an end field configured to receive an ending locationor a query (e.g., a query concerning the end location of the route).

In some embodiments, the popup view for the first field includes (836) alist of prior query inputs received in the first field (e.g., recentspopup view 540-5 in FIG. 5P), and the popup view for the second fieldincludes a list of prior query inputs received in the second field(e.g., recents popup view 540-6 in FIG. 5T).

In some embodiments, the list of prior query inputs received in thefirst field is distinct from the list of prior query inputs received inthe second field (838). For example, in these embodiments, the list ofprior query inputs in recents popup view 540-5 in FIG. 5P is distinctfrom the list of prior query inputs in recents popup view 540-6 in FIG.5T. However, in some other embodiments, the same list of prior queryinputs is provided for both the first field (e.g., for specifying astarting point) and the second field (e.g., for specifying an endingpoint).

The operations described above with reference to FIGS. 6A-6B, 7A-7B, and8A-8C may be implemented by components depicted in FIGS. 1A-1C. Forexample, receiving operations 604 and 606, detecting operations 612 and614, and displaying operation 616 may be implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive display 112, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates event handler 180 associated with the detection of the eventor sub-event. Event handler 180 may utilize or call data updater 176 orobject updater 177 to update the internal state of application 136-1data. In some embodiments, event handler 180 accesses respective GUIupdater 178 to update what is displayed by the application. Similarly,it would be clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1C.

The operations in the information processing methods described above maybe implemented by running one or more functional modules in informationprocessing apparatus such as general purpose processors or applicationspecific chips. These modules, combinations of these modules, and/ortheir combination with information processing and storage hardware(e.g., as described above with respect to FIGS. 1A, 1B and 3) are allincluded within the scope of protection of the invention.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best utilize the invention andvarious embodiments with various modifications as are suited to theparticular use contemplated.

1-20. (canceled)
 21. A method, comprising: at a computing device with adisplay: displaying a map on the display; while displaying the map,displaying a popup view with a list of prior query inputs; detectingselection of a prior query input in the list of prior query inputs; andin response to detecting selection of the prior query input in the listof prior query inputs: initiating a search using the selected priorquery input; and displaying on the map one or more search results forthe selected prior query input.
 22. The method of claim 21, wherein thelist of prior query inputs is scrollable.
 23. The method of claim 21,including: in response to detecting selection of the prior query inputin the list of prior query inputs, ceasing to display the popup view.24. The method of claim 21, wherein the computing device includes atouch-sensitive surface and detecting selection of the prior query inputincludes detecting a gesture at a location on the touch-sensitivesurface that corresponds to the prior query input.
 25. The method ofclaim 21, wherein the computing device includes a touch-sensitivesurface, the method including: displaying a keyboard on the display;detecting a gesture at a location on the touch-sensitive surface thatcorresponds to the keyboard; and in response to detecting the gesture atthe location on the touch-sensitive surface that corresponds to thekeyboard, displaying a suggestion box that includes a list of suggestedquery inputs.
 26. The method of claim 25, wherein displaying thesuggestion box includes replacing the list of prior query inputs withthe list of suggested query inputs.
 27. The method of claim 25, whereinthe list of suggested query inputs is generated in accordance with inputreceived via the keyboard.
 28. The method of claim 27, whereingenerating the list of suggested query inputs includes identifying anentry in an address book stored in the computing device, the entry atleast partially matching the input received via the keyboard.
 29. Themethod of claim 27, wherein generating the list of suggested queryinputs includes obtaining suggested query inputs from a remote server.30. The method of claim 29, wherein the computing device includes atouch-sensitive surface and the popup view with the list of prior queryinputs is displayed in response to detecting a gesture at a location onthe touch-sensitive surface that corresponds to a recent queries icon.31. The method of claim 29, wherein the computing device includes atouch-sensitive surface and the popup view with the list of prior queryinputs is displayed in response to detecting a gesture at a location onthe touch-sensitive surface that corresponds to one of: a first fieldconfigured to receive a first query input and a second field configuredto receive a second query input.
 32. The method of claim 31, wherein thepopup view for the first field includes a list of prior query inputsreceived in the first field; and the popup view for the second fieldincludes a list of prior query inputs received in the second field. 33.The method of claim 30, wherein the list of prior query inputs receivedin the first field is distinct from the list of prior query inputsreceived in the second field.
 34. A computing device, comprising: adisplay; one or more processors; memory; and one or more programs,wherein the one or more programs are stored in the memory and configuredto be executed by the one or more processors, the one or more programsincluding instructions for: displaying a map on the display; whiledisplaying the map, displaying a popup view with a list of prior queryinputs; detecting selection of a prior query input in the list of priorquery inputs; and in response to detecting selection of the prior queryinput in the list of prior query inputs: initiating a search using theselected prior query input; and displaying on the map one or more searchresults for the selected prior query input.
 35. A graphical userinterface on a computing device with a display, a memory, and one ormore processors to execute one or more programs stored in the memory,the graphical user interface comprising: a map on the display; wherein:while displaying the map, a popup view with a list of prior query inputsis displayed; and in response to detecting selection of a prior queryinput in the list of prior query inputs: a search is initiated using theselected prior query input; and one or more search results for theselected prior query input are displayed on the map.
 36. A computerreadable storage medium storing one or more programs, the one or moreprograms comprising instructions, which when executed by a computingdevice with a display, cause the device to: display a map on thedisplay; while displaying the map, display a popup view with a list ofprior query inputs; detect selection of a prior query input in the listof prior query inputs; and in response to detecting selection of theprior query input in the list of prior query inputs: initiate a searchusing the selected prior query input; and display on the map one or moresearch results for the selected prior query input.